Method for apparatus for routing application programming interface (api) calls

ABSTRACT

A method and apparatus for routing Application Programming Interface (API) calls from a partner entity to a telephony service provider (TSP) network are provided herein. In some embodiments, a method for routing API calls may include receiving a first message including an API call and a partner API key used to authenticate the partner entity on the TSP network to access a partner API layer disposed on the TSP network, extracting the partner API key from the first message, performing an authentication process to authenticate an identity of the partner entity using at least the extracted partner API key, and routing the first message based on results of the authentication process. In some embodiments, the first message is routed to the partner API layer disposed on the TSP network when the identity of the partner entity is authenticated.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims benefit of U.S. provisional patent applicationSer. No. 61/791,285, filed Mar. 15, 2013, which is herein incorporatedby reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

Embodiments of the present invention generally relate to a scalable,secure and reliable partner interface system for establishing andauthenticating third party business service providers, and receiving androuting API calls to and from a telephony service provider's network.

2. Description of the Related Art

Telephony service providers (TSP) may partner with external serviceproviders to provide telephony services to each other's customers. Insome situations, service providers may sign up customers for telephonyservice but may not possess the capability or capacity to handle certaintypes or volumes of service. The service provider may partner withanother TSP to provide those telephony services, or other types ofservices. In other situations, a TSP may partner with regional businesspartners to sign up customers on the TSP's behalf.

To facilitate the above-mentioned partnership, as well as applicationsof third party business service providers, a scalable, secure andreliable infrastructure and interface to the TSP network is needed.Accordingly, there exists a need in the art for a method and apparatusto support provisioning of accounts, devices, services and features inthe TSP network.

SUMMARY OF THE INVENTION

A method and apparatus for routing Application Programming Interface(API) calls from a partner entity to a telephony service provider (TSP)network are provided herein. In some embodiments, a method for routingAPI calls may include receiving a first message including an API calland a partner API key used to authenticate the partner entity on the TSPnetwork to access a partner API layer disposed on the TSP network,extracting the partner API key from the first message, performing anauthentication process to authenticate an identity of the partner entityusing at least the extracted partner API key, and routing the firstmessage based on results of the authentication process. In someembodiments, the first message is routed to the partner API layerdisposed on the TSP network when the identity of the partner entity isauthenticated.

In some embodiments, an apparatus for routing API calls from a partnerentity to a TSP network includes at least one processor, at least oneinput device, and at least one storage device storing processorexecutable instructions which, when executed by the at least oneprocessor, performs a method including receiving a first messageincluding an API call and a partner API key used to authenticate thepartner entity on the TSP network to access a partner API layer disposedon the TSP network, extracting the partner API key from the firstmessage, performing an authentication process to authenticate anidentity of the partner entity using at least the extracted partner APIkey, and routing the first message based on results of theauthentication process.

In some embodiments, a non-transient computer readable medium forstoring computer instructions that, when executed by at least oneprocessor causes the at least one processor to perform a method forrouting API calls may include receiving a first message including an APIcall and a partner API key used to authenticate the partner entity onthe TSP network to access a partner API layer disposed on the TSPnetwork, extracting the partner API key from the first message,performing an authentication process to authenticate an identity of thepartner entity using at least the extracted partner API key, and routingthe first message based on results of the authentication process.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the presentinvention can be understood in detail, a more particular description ofthe invention, briefly summarized above, may be had by reference toembodiments, some of which are illustrated in the appended drawings. Itis to be noted, however, that the appended drawings illustrate onlytypical embodiments of this invention and are therefore not to beconsidered limiting of its scope, for the invention may admit to otherequally effective embodiments.

FIG. 1 depicts a block diagram of a telecommunication network, inaccordance with embodiments consistent with the present application;

FIG. 2 depicts a block diagram of an exemplary secure proxy layer, inaccordance with embodiments consistent with the present application;

FIG. 3A depicts a flowchart for establishing and authenticating partnersaccording to one or more embodiments of the invention;

FIG. 3B depicts a flowchart for receiving and routing API callsaccording to one or more embodiments of the invention; and

FIG. 4 is a detailed block diagram of a computer system, according toone or more embodiments.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. The figures are not drawn to scale and may be simplifiedfor clarity. It is contemplated that elements and features of oneembodiment may be beneficially incorporated in other embodiments withoutfurther recitation.

DETAILED DESCRIPTION

Embodiments of the present invention generally relate to a scalable,secure and reliable partner interface system for establishing partnersand provisioning telephony customers in a telephony service provider'snetwork. Some embodiments of the present invention include a partner APIthat may be accessed by a partner service provider (referred to hereinas the partner), to provide a set of services and or modules thatsupport provisioning of accounts, devices, services and features usingthe TSP network. For example, a TSP may agree with a partner to provideVoice over Internet Protocol (VoIP) network services to customers thatsign up for service through the partner using the TSP's VoIP network. Inother examples, other types of services providers may agree to provideservices to customers signed by external partners. Although describedherein in terms of telephony service providers, the TSPs may provideother types of services that embodiments of the present invention may beused with, for example, Web-based services and the like.

When a TSP establishes a service relationship with a partner on whosebehalf the TSP will provide telephony services to customers that thepartner signs up, the partner first needs to be setup to securely accessthe TSP network via an API and related systems. Furthermore, when apartner signs up a customer for telephony service that is to be providedby the TSP, certain information (also described as entities herein) needto be managed in the TSP network including, but not limited to, partnerinformation, customer account information, service type information,device information, and the like.

Partner information may be associated with a specific partner in thesystem. Each partner has a unique partner ID and associated securitykeys. When a partner is added to the system, the set of applicablefeatures and default feature values can be specified for the partner.

Customer account information may be contained in information objectsrepresenting customers in the TSP network. Each customer may be given aglobally unique network account number within the TSP system. In someembodiments, this network account information may not be the same as thepartner's Customer Relationship management (CRM) information regardingthe customer or billing account information which may be housed indifferent partner Business Support Systems (BSS).

Service type information may be contained in information objectsrepresenting the types of telephony service the TSP can provide, forexample, VoIP, short message service (SMS), and the like. Each servicetype may be represented by a globally unique service Identifier. Aservice type may include a number of other attributes related to thetype of service represented. The service identifier identifies aninstance of a service type that is associated with a partner account.For example partner account #1001 may have two service types, VoIP andSMS, with service identifiers #8001 and #8002, respectively. Similarly,partner account #1002 may have two service types, VoIP and SMS, withservice identifiers #8003 and #8004 respectively.

Device information may include information about the hardware devicesused, if any, in providing the service that the customer signed up for.For example, if a customer signs up for VoIP service, the deviceinformation may include information regarding a VoIP Telephony adapteron which service is provided. In some embodiments, devices areidentified by their globally unique MAC address. It is noted that notall service types require hardware devices.

For the above information objects, there are various operations that maybe performed on each object. Such operations may include adding a newentity in to the system and associating them with other entities,changing the settings for an existing entity, change the status of anentity, and retrieving the settings for a given entity.

To create, access and manage the aforementioned information, exemplaryembodiments include a security proxy layer that provides scalable,secure and reliable access to a partner API layer, and is describedbelow.

Some portions of the detailed description which follow are presented interms of operations on binary digital signals stored within a memory ofa specific apparatus or special purpose computing device or platform. Inthe context of this particular specification, the term specificapparatus or the like includes a general purpose computer once it isprogrammed to perform particular functions pursuant to instructions fromprogram software. In this context, operations or processing involvephysical manipulation of physical quantities. Typically, although notnecessarily, such quantities may take the form of electrical or magneticsignals capable of being stored, transferred, combined, compared orotherwise manipulated. It has proven convenient at times, principallyfor reasons of common usage, to refer to such signals as bits, data,values, elements, symbols, characters, terms, numbers, numerals or thelike. It should be understood, however, that all of these or similarterms are to be associated with appropriate physical quantities and aremerely convenient labels. Unless specifically stated otherwise, asapparent from the following discussion, it is appreciated thatthroughout this specification discussions utilizing terms such as“processing,” “computing,” “calculating,” “determining” or the likerefer to actions or processes of a specific apparatus, such as a specialpurpose computer or a similar special purpose electronic computingdevice. In the context of this specification, therefore, a specialpurpose computer or a similar special purpose electronic computingdevice is capable of manipulating or transforming signals, typicallyrepresented as physical electronic or magnetic quantities withinmemories, registers, or other information storage devices, transmissiondevices, or display devices of the special purpose computer or similarspecial purpose electronic computing device.

FIG. 1 depicts a block diagram of a system 100 that includes a partnerBusiness Support Systems (BSS) 102, a secure proxy layer 104, and apartner API layer 106.

In some embodiments, the partner BSS 102 may be disposed on thepartner's network 114. A customer 108 may subscribe for telephonyservice or login to an existing account using the partner BSS 102. Insome embodiments, the partner API layer may be disposed on the TSPnetwork 112. The telephony service that is to be provided to thecustomer may be provided by the TSP network 112. In addition, a partnerservice agent 110 may subscribe for a new account on behalf of acustomer 108 or may access existing customers account information (e.g.,to add, modify, remove features, etc.) through the partner BSS.

In some embodiments, the secure proxy layer 104 will perform keymanagement for partners and will authenticate/authorize all requestsfrom the partner BSS 102 before authorizing/allowing access to thepartner API layer 106. The secure proxy layer 104 can also perform otherAPI management tasks like data throttling of API calls if required. Insome embodiments, the throttling rate of API calls can be individuallyconfigured on a per partner level, or on particular sets of partnersgrouped together based on one or more common features between thepartners (e.g., partners for a specific country, size of partner, andthe like). In some embodiments, the secure proxy layer 104 may be acloud based security proxy into the partner API layer 106. In otherembodiments, the secure proxy layer 104 may be located within the TSPnetwork 112.

As new partners are added there will be an “onboarding” process requiredto setup the new partner via the secure proxy layer 104. This willinvolve generating security keys for communication between partner BSS102 and the TSP network 112 and between the TSP network 112 and partnerBSS 102. In some embodiments, the partner will need to provide list ofservers/devices (e.g., a whitelist of approved devices identified by aMAC address or an Internet Protocol (IP) address) that will be sendingrequests to partner API layer 106 via the secure proxy layer 104.Similarly, for embodiments where 104 is a cloud based service, thesecure proxy layer 104 may be required to provide a whitelist of serversto the partner API layer 106 that can send authenticated requests topartner API layer 106.

With the secure proxy layer 104 as a proxy between the partner BSS 102and the partner API layer 106 on the TSP network, the partner BSS 102will be able to access API services such as adding/modifying networkaccounts, services, devices, and features. This may be done by makingpredefined calls to API modules disposed in partner API layer 106. Inaddition, the partner API layer 106 will also be able to access customerdata stored in partner BSS 102 by also making predefined API modulecalls (e.g., call backs). In some embodiments, the secure proxy layer104 will authenticate the call backs using a separate API key beforerouting the requests to the partner BSS 102. The secure proxy layer 104may be required to provide a whitelist of servers to the BSS 102 thatthat can send authenticated requests to partner BSS 102. All API modulecalls from the partner BSS 102 that are made directly to the partner APIlayer 106 will be redirected through the secure proxy layer 104. In someembodiments, the redirected calls may be delivered over a HypertextTransfer Protocol Secure (HTTPS) connection.

For each of the TSP's partners established, at least one API key will begenerated by the secure proxy layer 104. In some embodiments, the secureproxy layer 104 may include an API management dashboard tocreate/establish a partner and create said keys. In some embodiments, afirst API key is used by partner BSS 102 to access the partner API layer106, and a second API key is used by the partner API layer 106 to callback the partner BSS 102. These bidirectional communications are securedby the API keys created by the secure proxy layer 104. In someembodiments, the API keys, together with a partner ID, may be embeddedinto a Simple Object Access Protocol (SOAP) envelope body and deliveredin service request messages. When the secure proxy layer 104 receivesmessages from partner BSS 102 or the partner API layer 106, the secureproxy layer 104 will automatically extract the API key values from theSOAP message body and validate it against the key value generated forthe partner. In some embodiments, only API key matched messages willpass through the secure proxy layer 104 to appropriate endpoints. Insome embodiments, non-matching messages will be discarded with aresponse message “Access Denied” or the equivalent.

As shown in FIG. 2, the secure proxy layer 104 may include one or moreCentral Processing Units (CPU) 124, support circuits 126, and memory128. The CPU 124 may comprise one or more commercially availablemicroprocessors or microcontrollers that facilitate data processing andstorage. The various support circuits 126 facilitate the operation ofthe CPU 124 and include one or more clock circuits, power supplies,cache, input/output circuits, and the like. The memory 128 comprises atleast one of Read Only Memory (ROM), Random Access Memory (RAM), diskdrive storage, optical storage, removable storage and/or the like. Insome embodiments, the memory 128 comprises an operating system 132,partner setup module 134, API key authentication module 136, approvedserver list 138, throttling module 140, and API call routing module 142.

The operating system (OS) 132 generally manages various computerresources (e.g., network resources, file processors, and/or the like).The operating system 132 is configured to execute operations on one ormore hardware and/or software modules, such as Network Interface Cards(NICs), hard disks, virtualization layers, firewalls and/or the like.Examples of the operating system 132 may include, but are not limitedto, LINUX, MAC OSX, BSD, UNIX, MICROSOFT WINDOWS, IOS, ANDROID and thelike.

The partner setup module 134 creates the one or more API keys asdescribed above when establishing a new partner with the TSP. The APIkey authentication module 136 may be used to authenticate the API keysreceived. After the API keys are matched/authenticated, the API callrouting module 142 may route the API calls to their appropriatedestination.

In some embodiments, after a partner is authenticated, additionalauthorization may be performed for each API call made by the partner.Specifically, when a partner is authenticated and identified, thepartner may only be authorized to use a subset of the total API callsavailable on the partner API layer 106. The API features and functionsthat are authorized to be used by that partner are the only ones thatwill be acted upon by the partner API layer 106. If a partner requests afeature/function that it is not authorized for use, the partner APIlayer 106 will respond with an error and will not route the message tothe relevant downstream internal network components. In someembodiments, the partner API layer 106 may perform the additionalpartner API call authorization described above. The API callauthorization information is stored in a database table. The informationis checked for each API call. In some embodiments, the API callauthorization database table is set up when provisioning a partner. Thetable can be modified at any time to change permissions. Since thesepermissions are typically governed by business agreements, the changesare usually few and far in between, and thus, in some embodiments, thechanges may be made manually. In other embodiments, the API callauthorization database table may be updated automatically.

Before routing the API calls to their appropriate destination, thesecure proxy layer 104 may authenticate the identity of the partner BSSservers/devices against an approved server list 138. If the originatingserver of the API call to the partner API layer 106 from the partner BSS102 is not on the list, the API call may return an “ACCESS DENIED” errormessage, or other error message including the reason for the denial ofaccess.

In some embodiments, if the volume of API calls becomes a problem forthe partner API layer 106, a throttling module 140 may be used tothrottle the number of API calls to or from the partner API layer 106.

In some embodiments, the partner API layer 106 may perform functionsthat provide performance data and business intelligence associated withuse of the partner API layer 106. Specifically, in some embodiments, thepartner API layer 106 may gather timing data for each API call. Suchtiming data may provide insight regarding performance issues andbottlenecks in the API system. In some embodiments, the secure proxylayer 104 may gather counts and information regarding the different APIcalls made by each partner (both authorized and unauthorized calls).Such API call information may provide business intelligence with respectto new customer signups or terminations, API calls/features most oftenused/modified, and the like.

A method 300 in accordance with the subject invention is illustrated inFIG. 3A which depicts a flowchart having a series of steps forestablishing and authenticating partners in a TSP's network. In detail,the method 300 starts at 302 and proceeds to 304 where a request toestablish a new partner is received. In some embodiments, the request isreceived by the secure proxy layer 104 from the partner BSS 102. Therequest may be an HTTP request in the form of SOAP or RepresentationalState Transfer (REST) message, or embedded in the body of the SOAP orREST message or similar type of message. In some embodiments, therequest may be sent over a Hypertext Transfer Protocol Secure (HTTPS)connection or over a dedicated Virtual Private Network (VPN) connectionbetween the partner BSS 102 and the secure proxy layer 104.

At 306, the secure proxy layer 104 may generate a first API key used toprovide the partner access to a partner API layer 106. In someembodiments, the API key may be an encrypted key or secure tokengenerated which is used by the TSP to authenticate the partner. At 308the generated partner API key is sent to the partner. The API key may bein the form of a SOAP or a REST message, or embedded in the body of theSOAP or REST message or similar type of message. In some embodiments,the request may be sent over a HTTPS connection or over a dedicated VPNconnection between the partner BSS 102 and the secure proxy layer 104.In response to the request to establish a new partner, the secure proxylayer 104 and/or modules/devices disposed on the TSP network will createpartner information objects that include a unique partner ID associatedwith the generated API keys for the partner. In addition, whenestablishing a new partner on the TSP network, the partner may berequested to provide list of servers/devices (i.e., a whitelist ofapproved devices identified by a MAC address for example) that will besending/generating API calls to partner API layer 106 via the secureproxy layer 104. Additional information regarding the partner may alsobe stored in the partner information objects such as partner contactinformation, customer billing rates, authorized API calls, and the like.The method 300 ends at 310

After the partner has been established, the partner can set up (i.e.,provision) and manage telephony customers on the TSP network by makingAPI calls to the partner API layer 106 via the secure proxy layer 104.

For example, FIG. 3B depicts a flowchart of a method 301 for receivingand routing API calls according to one or more embodiments of theinvention. In detail, the method 301 starts at 350 and proceeds to 352,where the secure proxy layer 104 may receive one or more API calls fromthe partner including the generated API key. In some embodiments, theAPI keys, together with a partner ID, may be embedded into a SOAPenvelope body and delivered in service request messages as describedabove. The API calls received at 352 may include requests toestablishing new customers and managing and provisioning telephonyservices for customers on the TSP's network. At 354, after the secureproxy layer 104 receives messages from partner BSS 102 or the partnerAPI layer 106, the secure proxy layer 104 will perform an authenticationprocess to authenticate the identity of the partner entity. In someembodiments, the authentication process may automatically extract theAPI key value(s) from the message body and validate it against the keyvalue(s) generated for the partner to authenticate the partner. In someembodiments, validating the API key values generated may includeperforming a direct comparison of API key value pairs. In otherembodiments, information derived using the API keys may be used toauthenticate the partner entity (e.g., such as hash values, and thelike). At 356, if the partner is authenticated, the API key matchedmessages will pass through the secure proxy layer 104 and be routed bythe secure proxy layer 104 to the partner API layer at 358. The partnerAPI layer will then direct the messages to appropriate endpoints on theTSP network. As noted above, the API call may be in the form of a SOAPor REST message. In some embodiments, the secure proxy layer 104 willtransparently pass the message after authentication to the partner APIlayer, which will then extract relevant fields and construct a newmessage(s) and send it to downstream components. If the partner is notauthenticated at 356, non-matching messages may be discarded with aresponse message being sent to the partner denying access to the partnerAPI at 360. The method 301 ends at 362.

The embodiments of the present invention may be embodied as methods,apparatus, electronic devices, and/or computer program products.Accordingly, the embodiments of the present invention may be embodied inhardware and/or in software (including firmware, resident software,micro-code, and the like), which may be generally referred to herein asa “circuit” or “module”. Furthermore, the present invention may take theform of a computer program product on a computer-usable orcomputer-readable storage medium having computer-usable orcomputer-readable program code embodied in the medium for use by or inconnection with an instruction execution system. In the context of thisdocument, a computer-usable or computer-readable medium may be anymedium that can contain, store, communicate, propagate, or transport theprogram for use by or in connection with the instruction executionsystem, apparatus, or device. These computer program instructions mayalso be stored in a computer-usable or computer-readable memory that maydirect a computer or other programmable data processing apparatus tofunction in a particular manner, such that the instructions stored inthe computer usable or computer-readable memory produce an article ofmanufacture including instructions that implement the function specifiedin the flowchart and/or block diagram block or blocks.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus or device. More specificexamples (a non exhaustive list) of the computer-readable medium includethe following: hard disks, optical storage devices, magnetic storagedevices, an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a compact disc read-only memory (CD-ROM).

Computer program code for carrying out operations of the presentinvention may be written in an object oriented programming language,such as Java®, Smalltalk or C++, and the like. However, the computerprogram code for carrying out operations of the present invention mayalso be written in conventional procedural programming languages, suchas the “C” programming language and/or any other lower level assemblerlanguages. It will be further appreciated that the functionality of anyor all of the program modules may also be implemented using discretehardware components, one or more Application Specific IntegratedCircuits (ASICs), or programmed Digital Signal Processors ormicrocontrollers.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the present disclosure and its practical applications, tothereby enable others skilled in the art to best utilize the inventionand various embodiments with various modifications as may be suited tothe particular use contemplated.

FIG. 4 depicts a computer system 400 that can be utilized in variousembodiments of the present invention to implement the computer and/orthe display, according to one or more embodiments.

Various embodiments of method and apparatus for routing calls based uponinternal network conditions and/or external carrier network information,as described herein, may be executed on one or more computer systems,which may interact with various other devices. One such computer systemis computer system 400 illustrated by FIG. 4, which may in variousembodiments implement any of the elements or functionality illustratedin FIGS. 1-3. In various embodiments, computer system 400 may beconfigured to implement methods described above. The computer system 400may be used to implement any other system, device, element,functionality or method of the above-described embodiments. In theillustrated embodiments, computer system 400 may be configured toimplement method 300 as processor-executable executable programinstructions 422 (e.g., program instructions executable by processor(s)410) in various embodiments.

In the illustrated embodiment, computer system 400 includes one or moreprocessors 410 a-410 n coupled to a system memory 420 via aninput/output (I/O) interface 430. Computer system 400 further includes anetwork interface 440 coupled to I/O interface 430, and one or moreinput/output devices 450, such as cursor control device 460, keyboard470, and display(s) 480. In various embodiments, any of the componentsmay be utilized by the system to receive user input described above. Invarious embodiments, a user interface may be generated and displayed ondisplay 480. In some cases, it is contemplated that embodiments may beimplemented using a single instance of computer system 400, while inother embodiments multiple such systems, or multiple nodes making upcomputer system 400, may be configured to host different portions orinstances of various embodiments. For example, in one embodiment someelements may be implemented via one or more nodes of computer system 400that are distinct from those nodes implementing other elements. Inanother example, multiple nodes may implement computer system 400 in adistributed manner.

In different embodiments, computer system 400 may be any of varioustypes of devices, including, but not limited to, personal computersystems, mainframe computer systems, handheld computers, workstations,network computers, application servers, storage devices, a peripheraldevices such as a switch, modem, router, or in general any type ofcomputing or electronic device.

In various embodiments, computer system 400 may be a uniprocessor systemincluding one processor 410, or a multiprocessor system includingseveral processors 410 (e.g., two, four, eight, or another suitablenumber). Processors 410 may be any suitable processor capable ofexecuting instructions. For example, in various embodiments processors410 may be general-purpose or embedded processors implementing any of avariety of instruction set architectures (ISAs). In multiprocessorsystems, each of processors 410 may commonly, but not necessarily,implement the same ISA.

System memory 420 may be configured to store program instructions 422and/or data 432 accessible by processor 410. In various embodiments,system memory 420 may be implemented using any suitable memorytechnology, such as static random access memory (SRAM), synchronousdynamic RAM (SDRAM), non-volatile/Flash-type memory, or any other typeof memory. In the illustrated embodiment, program instructions and dataimplementing any of the elements of the embodiments described above maybe stored within system memory 420. In other embodiments, programinstructions and/or data may be received, sent or stored upon differenttypes of computer-accessible media or on similar media separate fromsystem memory 420 or computer system 400.

In one embodiment, I/O interface 430 may be configured to coordinate I/Otraffic between processor 410, system memory 420, and any peripheraldevices in the device, including network interface 440 or otherperipheral interfaces, such as input/output devices 450. In someembodiments, I/O interface 430 may perform any necessary protocol,timing or other data transformations to convert data signals from onecomponent (e.g., system memory 420) into a format suitable for use byanother component (e.g., processor 410). In some embodiments, I/Ointerface 430 may include support for devices attached through varioustypes of peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some embodiments, the function of I/Ointerface 430 may be split into two or more separate components, such asa north bridge and a south bridge, for example. Also, in someembodiments some or all of the functionality of I/O interface 430, suchas an interface to system memory 420, may be incorporated directly intoprocessor 410.

Network interface 440 may be configured to allow data to be exchangedbetween computer system 400 and other devices attached to a network(e.g., network 490), such as one or more external systems or betweennodes of computer system 400. In various embodiments, network 490 mayinclude one or more networks including but not limited to Local AreaNetworks (LANs) (e.g., an Ethernet or corporate network), Wide AreaNetworks (WANs) (e.g., the Internet), wireless data networks, some otherelectronic data network, or some combination thereof. In variousembodiments, network interface 440 may support communication via wiredor wireless general data networks, such as any suitable type of Ethernetnetwork, for example; via telecommunications/telephony networks such asanalog voice networks or digital fiber communications networks; viastorage area networks such as Fibre Channel SANs, or via any othersuitable type of network and/or protocol.

Input/output devices 450 may, in some embodiments, include one or moredisplay terminals, keyboards, keypads, touchpads, scanning devices,voice or optical recognition devices, or any other devices suitable forentering or accessing data by one or more computer systems 400. Multipleinput/output devices 450 may be present in computer system 400 or may bedistributed on various nodes of computer system 400. In someembodiments, similar input/output devices may be separate from computersystem 400 and may interact with one or more nodes of computer system400 through a wired or wireless connection, such as over networkinterface 440.

In some embodiments, the illustrated computer system may implement anyof the methods described above, such as the methods illustrated by theflowchart of FIG. 3. In other embodiments, different elements and datamay be included.

Those skilled in the art will appreciate that computer system 400 ismerely illustrative and is not intended to limit the scope ofembodiments. In particular, the computer system and devices may includeany combination of hardware or software that can perform the indicatedfunctions of various embodiments, including computers, network devices,Internet appliances, PDAs, wireless phones, pagers, and the like.Computer system 400 may also be connected to other devices that are notillustrated, or instead may operate as a stand-alone system. Inaddition, the functionality provided by the illustrated components mayin some embodiments be combined in fewer components or distributed inadditional components. Similarly, in some embodiments, the functionalityof some of the illustrated components may not be provided and/or otheradditional functionality may be available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or on storage while beingused, these items or portions of them may be transferred between memoryand other storage devices for purposes of memory management and dataintegrity. Alternatively, in other embodiments some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated computer system via inter-computercommunication. Some or all of the system components or data structuresmay also be stored (e.g., as instructions or structured data) on acomputer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described above. Insome embodiments, instructions stored on a computer-accessible mediumseparate from computer system 400 may be transmitted to computer system400 via transmission media or signals such as electrical,electromagnetic, or digital signals, conveyed via a communication mediumsuch as a network and/or a wireless link. Various embodiments mayfurther include receiving, sending or storing instructions and/or dataimplemented in accordance with the foregoing description upon acomputer-accessible medium or via a communication medium. In general, acomputer-accessible medium may include a storage medium or memory mediumsuch as magnetic or optical media, e.g., disk or DVD/CD-ROM, volatile ornon-volatile media such as RAM (e.g., SDRAM, DDR, RDRAM, SRAM, and thelike), ROM, and the like.

The methods described herein may be implemented in software, hardware,or a combination thereof, in different embodiments. In addition, theorder of methods may be changed, and various elements may be added,reordered, combined, omitted or otherwise modified. All examplesdescribed herein are presented in a non-limiting manner. Variousmodifications and changes may be made as would be obvious to a personskilled in the art having benefit of this disclosure. Realizations inaccordance with embodiments have been described in the context ofparticular embodiments. These embodiments are meant to be illustrativeand not limiting. Many variations, modifications, additions, andimprovements are possible. Accordingly, plural instances may be providedfor components described herein as a single instance. Boundaries betweenvarious components, operations and data stores are somewhat arbitrary,and particular operations are illustrated in the context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within the scope of claims that follow. Finally,structures and functionality presented as discrete components in theexample configurations may be implemented as a combined structure orcomponent. These and other variations, modifications, additions, andimprovements may fall within the scope of embodiments as defined in theclaims that follow

While the foregoing is directed to embodiments of the present invention,other and further embodiments of the invention may be devised withoutdeparting from the basic scope thereof, and the scope thereof isdetermined by the claims that follow.

1. A method for routing Application Programming Interface (API) callsfrom a partner entity to a telephony service provider (TSP) networkcomprising: receiving a first message including a partner API key usedto authenticate the partner entity on the TSP network to access apartner API layer disposed on the TSP network; extracting the partnerAPI key from the first message; performing an authentication process toauthenticate an identity of the partner entity using at least theextracted partner API key; and routing the first message based onresults of the authentication process.
 2. The method of claim 1, whereinthe first message is routed to the partner API layer disposed on the TSPnetwork when the identity of the partner entity is authenticated.
 3. Themethod of claim 1, wherein the first message is discarded and access tothe partner API layer is denied when the identity of the partner entityis not authenticated.
 4. The method of claim 3, further comprising:sending a response message to the partner entity denying access to thepartner API layer.
 5. The method of claim 1, wherein the authenticationprocess includes validating the extracted partner API key against an APIkey generated for the partner entity.
 6. The method of claim 1, whereinthe first message is a service request message, and wherein the partnerAPI key is embedded in a Simple Object Access Protocol (SOAP) envelopebody of the service request message.
 7. The method of claim 6, wherein apartner ID identifying the partner entity is further included in theSOAP envelope body along with the partner API key.
 8. The method ofclaim 1, wherein the method is performed by a cloud based securityproxy.
 9. The method of claim 2, wherein authenticated partner entitiesare authorized to access TSP network services including at least one ofadding or modifying at least one of network accounts, network services,network devices, and network features.
 10. The method of claim 1,wherein prior to receiving the first message, the method furthercomprises generating the partner API key used to provide the partnerentity access to the partner API layer.
 11. The method of claim 1,wherein prior to receiving the first message, the method furthercomprises receiving a whitelist of partner entity devices that will besending requests to the partner API layer.